Systems, Methods, and Software for Mobile Video Display and Management

ABSTRACT

A system, method, and software for mobile video display and management includes acquiring a plurality of streams of video data from a plurality of cameras. The plurality of streams of video data are stored and plurality of selected streams of video data that includes at least one stream of recorded video data and at least one stream of live video data are presented in a graphical user interface of a remote device.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a Continuation of U.S. patent application Ser. No.14/021,710, filed on Sep. 9, 2013, and which claims the benefit of U.S.provisional patent application No. 61/698,672, filed on Sep. 9, 2012.The entire contents of each of these applications is hereby incorporatedby reference.

BACKGROUND

The present disclosure relates to the field of video display andmanagement systems, and in particular, to mobile video display andmanagement.

Video systems often include video recording devices, encoders, decoders,and client devices, These devices, when combined, allow for videoprocessing of a recorded scene.

Mobile devices can add flexibility to monitor and/or analyze of capturedvideo data. However, currently available systems, methods, and softwarefor mobile video display and management are limited in functionality andutility for video display and management. Therefore, new systems andtechniques are needed for mobile video display and management aredesired.

BRIEF DISCLOSURE

An embodiment of a method of mobile video display and managementincludes acquiring a plurality of streams of video data from a pluralityof cameras. Each of the plurality of streams of video data is stored asrecorded video data. A list of a plurality of cameras with availablerecorded video data is presented at a remote device. A list of aplurality of cameras with an available stream of video data is presentedat a remote device. A first selection of recorded video data forpresentation at the remote devices is received. A second selection of anavailable stream of video data, playback at the remote device isreceived. The video data of at least the selected recorded video dataand the selected available stream of video data are presented at theremote device.

A system for mobile video display and management includes a plurality ofvideo cameras that each capture a stream of video data. A video serverreceives and stores the streams of video data from each of the pluralityof video cameras as recorded video data. A mobile device includes agraphical display upon which a graphical user interface is presented.The graphical user interface is configured to present a plurality ofvideo playback tiles to present streaming video data. At least one videoplayback tile presents the stream of video data from one of theplurality of video cameras and at least one video playback tile presentsa stream of recorded video data from the video server.

A non-transient computer readable medium is programed with computerreadable code that upon execution by a computer processor causes theprocessor to initialize a graphical user interface presented on agraphical display of a mobile device to present a plurality of videopresentation tiles. A stream of video data is received from a videocamera in near-real time. The received stream of video data from a videocamera in near-real time is presented in one of the plurality of videopresentation tiles. A stream of recorded video data captured by videocamera and stored on a video server is received. A received stream ofrecorded video data is presented in one of the plurality of videopresentation tiles.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a system diagram that depicts an exemplary embodiment of asystem for mobile video display and management.

FIG. 2 is a system diagram that depicts an exemplary embodiment of acomputing system exemplarily for executing an embodiment of a method orsoftware for mobile video display and management.

FIG. 3 is a flowchart that depicts exemplary embodiment of a method ofmobile video display.

FIG. 4 is a flowchart that depicts an exemplary embodiment of a methodof mobile video management.

FIG. 5 depicts an exemplary embodiment of a screen shot of a list ofavailable cameras in a graphical user interface.

FIG. 6 depicts an exemplary embodiment of a screen shot of a selectionof a start time and end time for recorded video data in a graphical userinterface,

FIG. 7 depicts an exemplary embodiment of a screen shot of a graphicaluser interface for mobile video display and management.

FIG. 8 depicts an exemplary embodiment of a screen shot of a graphicaluser interface presenting multiple streams of video data on a mobiledevice.

FIG. 9 depicts an exemplary embodiment of a screen shot of a graphicaluser interface presenting a plurality of video presentation tilelayouts.

DETAILED DISCLOSURE

FIG. 1 depicts an exemplary embodiment of a system 10 for mobile videodisplay and management. The system 10 includes a plurality of videocamera 12 located at a remote location 14. In embodiments, the videocameras may be any of a variety of digital video cameras, including FPF,codec, resolution, and other types of cameras. The cameras 12 capturedigital video data and stream the video data across a communicationnetwork 16 to a video server 18 at which the digital video data isstored as recorded video data. The recorded video data can include timestamps that identify the times at which the video data was acquired bythe camera 12.

while the remote location 14 is generally depicted as a single locationat whick all of the cameras 12 are located, it will be understood thatthis is not intended to be limiting on the scope of the presentdisclosure as cameras 12 may be distributed at a plurality of locations.Any number of cameras 12 may be distributed at these locations and theacquired digital video data of which may be transferred across thecommunication network 16 to be stored at the video server 18. In anexemplary embodiment, the communication network 16 may include a localarea network (LAN), a wide area network (WAN), internet protocol, orcellular data connection in non-limiting exemplary embodiment. In anembodiment disclosed herein, the video server uses HTTP Live Streaming(HLS) protocol to enable the presentation of live HD video streaming.

A mobile device 20 is further communicatively connected to thecommunication network 16, and thus to the cameras 12 and the videoserver 18, as described in further detail herein. In non-limitingembodiments, the mobile device 20 may be any of a variety of mobiledevices, including, but not limited to a smart phone, a tablet computer,or a laptop computer. The mobile device 20 includes a graphical display22 that is configured to present video data in a graphical userinterface (GUI) 24 presented on the graphical display 22. Inembodiments, the graphical display 22 may be a touch-sensitive graphicaldisplay that operates as a user input device in connection with the GUI24, as may be described in further detail herein. The mobile device 20is configured to receive live video data 26 and recorded video data 28from the communication network 16 as described in farther detail herein.

Disclosed herein is a mobile application for execution on a mobilecommunication device that provides for mobile video display andmanagement. A non-limiting example of such a mobile application is theNextiva Mobile Application for Nextiva Video Management Software fromVerint. Nextiva Mobile™ is a mobile client application from Verint thatenables organizations to view Nextiva Video Management Software™ fromtheir Apple iOS-based devices, including the iPad and iPhone. Inexemplary embodiments of mobile applications, other operating systemsmay be supported, such as Android, Palm, Blackberry, and any othersuitable operating system. An embodiment of a mobile application allowssecurity operators to remotely access video and enhance operationalefficiency and effectiveness by viewing live and recorded video frommultiple cameras simultaneously. An exemplary embodiment furtherprovides 10 pre-defined screen layout options, zoom in or outcapabilities, and the management of most used and/or recent cameraviews. With embodiments of this mobile client application, users canstay connected and informed.

In an embodiment, the mobile application may be implemented on acomputing device, such as a mobile phone, tablet computer, laptopcomputer, ultra-book, desktop computer, or any other suitable computingdevice. FIG. 2 illustrates computing system 100, representative of asuitable computing system for executing an exemplary embodiment of themobile application, as well as other mobile applications, exemplarilythe computing system 100 may be the mobile device as depicted in FIG. 1.

Computing system 100 includes processing system 101, storage system 103,software 105, communication interface 107, and user interface 109.Processing system 101 is operatively coupled with storage system 103,communication interface 107, and user interface 109. Processing system101 loads and executes software 105 from storage system 103. Whenexecuted by computing system 100 in general, and processing system 101in particular, software 105 directs computing system 100 to operate asdescribed herein for application 111 or operating system 113. Computingsystem 100 may optionally include additional devices, features, orfunctionality not discussed here for purposes of brevity and clarity,but as would be recognized by a person having ordinary skill in the art.

Referring still to FIG. 2, processing system 101 may comprise amicroprocessor and other circuitry that retrieves and executes software105 from storage system 103. Processing system 101 may be implementedwithin a single processing device but may also be distributed acrossmultiple processing devices or sub-systems that cooperate in executingprogram instructions. Examples of processing system 101 include generalpurpose central processing units, application specific processors, andlogic devices, as well as any other type of processing device,combinations of processing devices, or variations thereof.

Storage system 103 may comprise any storage media readable by processingsystem 101 and capable of storing software 105. Storage system 103 mayinclude volatile and nonvolatile, removable and non-removable mediaimplemented in any method or technology for storage of information, suchas computer readable instructions, data structures, programimplementations of this description. Examples of such factors mayinclude, but are not limited to the technology used to implement thestorage media of storage system 103 and whether the computer-storagemedia are characterized as primary or secondary storage.

For example, if the computer-storage media are implemented assemiconductor based memory, software 105 may transform the physicalstate of the semiconductor memory when the program is encoded therein.For example, software 105 may transform the state of transistors,capacitors, or other discrete circuit elements constituting thesemiconductor memory. A similar transformation may occur with respect tomagnetic or optical media. Other transformations of physical media arepossible without departing from the scope of the present description,with the foregoing examples provided only to facilitate this discussion.

It should be understood that computing system 100 is generally intendedto represent a computing system with which software 105 is deployed andexecuted in order to implement mobile application 200 (and variationsthereof). Embodiments of the mobile application 200 are describedherein, exemplarily with respect to FIG. 3. However, computing system100 may also represent any computing system on which software 105 maybestaged and from where software 105 may be distributed, transported,downloaded, or otherwise provided to yet another computing system fordeployment and execution, or yet additional distribution.

Referring again to FIG. 2, communication interface 107 may includecommunication connections and devices that allow for communicationbetween computing system 100 and other computing systems (not shown)over a communication network or collection of networks (not shown).Examples of connections and devices that together allow for inter-systemcommunication may include network interface cards, antennas, poweramplifiers, RF circuitry, transceivers, and other communicationcircuitry. The aforementioned network, connections, and devices are wellknown and need not be discussed at length here.

User interface 109 may include a mouse, a voice input device, a touchinput device for receiving a gesture from a user, a motion input devicefor detecting non-touch gestures and other motions by a user and othercomparable input devices and associated processing elements capable ofreceiving user input from a user. Output devices such as a display,speakers, haptic devices, and other types of output devices may also beincluded in user interface 109. The aforementioned user input devicesare well known in the art and need not he discussed at length here. Userinterface 109 may also include associated user interface softwareexecutable by processing system 101 in support of the various user inputand output devices discussed above. Separately or in conjunction witheach other and other hardware and software elements, the user interfacesoftware and devices may provide a graphical user interface, a naturaluser interface, or any other kind of user interface.

FIG. 3 is a flowchart that depicts an exemplary embodiment of a methodof mobile video display. Exemplary embodiments of the method 200 may becarried out on the computer system 100 as described above with respectto FIG. 2 and as part of the system for mobile video display andmanagement 10 as described above with respect to FIG. 1.

The method 200 begins at 202 with the acquisition of real-time videodata. The video data is acquired by a plurality of video cameras thatmay be arranged at a remote location. In an exemplary embodiment, thevideo cameras may be deployed for surveillance, while in otherembodiments, the cameras may be deployed for a variety of other videomonitoring purposes. The video data acquired at 202 may be digital videodata that is transmitted from the video camera across a communicationsnetwork. It may be understood that in embodiments, an intermediatecomputer or processor may he located between each individual camera thatacquires the real-time video data and the communication network, andsuch a computer or processor may pre-process or package the video datain a manner to facilitate the transmission of the video data.

The acquired real-time video data is stored at 204, exemplarily asrecorded video data at a video server. The stored video data may bestored along with indications of the camera that acquired the video dataas well as at least one time stamp of when the video data was acquired.In an embodiment, the video server is an HLS video server that enablesstreaming of video data from the video server according to the HLSprotocol, enabling the streaming of high definition (HD) video to themobile device.

At 206 video playback at the remote device is initiated. As will bedescribed in further detail herein, a mobile app may be executed at theremote device such as to open a graphical user interface thatfacilitates the streaming presentation of video data, either recordedvideo data or live video data. In embodiments as disclosed in furtherdetail herein, the GUI presented at the remote device includes aplurality of video presentation tiles, each of which is configured topresent streaming video data. The GUI presented at the mobile device isfurther operable to present a list or a plurality of selections,exemplarily in a drop down menu or a list menu that identifies each ofthe cameras from which recorded video data is available and it isfurther operable to present a menu or list of cameras for which livevideo data is available.

At 208 a selection of recorded video for playback is received. In anembodiment, a user input is received with respect to a menu or list inthe GUI that presents the cameras from which available recorded video,stored at the video server, was obtained. At 210 a selection of livevideo for presentation is received. Exemplarily, the selection of livevideo for presentation is received by receiving a user input associatedwith a menu or list presented in the GUI of the cameras for which thelive video is available. At 212 multiple video data streams arepresented at the remote device. In an embodiment, the GUI at the remotedevice presents a plurality of video presentation tiles and at least onevideo presentation tile presents recorded video data and at leastanother of the video presentation tiles presents live video data, asselected at 208 and 210.

In an embodiment, a delay in the stream of live video data from thecameras that acquire real-time video data at 202 to the presentation ofthe live video data at the remote device at 212. This delay may be dueto buffering, available bandwidth, or other data connectivity issuesacross the communication network, between the cameras, or at the remotedevice. In other instances, this delay may be due to software analysisor processing that is performed on the video data prior to presentationat the remote device. Therefore, in an embodiment, the live video datagets presented in real-time or near-real time, while acknowledging thisdelay. In a non-limiting example, the delay may exemplarily be 5seconds, while in another mere exemplarily embodiment the delay is 30seconds; however, this is in no way intended to be limiting on the delaybetween acquisition and presentation of the live video data is disclosedin further detail herein. In embodiments, the live video data ispresented in the GUI at the remote device along with a time stamp of theactual time at which the video data was acquired. This can beinformative to a user of the mobile application in viewing the livevideo data to understand context of any delay in the presentation of thevideo data. Additionally, in an embodiment wherein multiples streams oflive video data are presented in the GUI at separate video presentationtiles, the live video data streams may have different length delaysexemplarily due to differences in processing of the video data, or theactual data connection from each of the cameras. Therefore, informationon the actual time of video acquisition is further helpful to the userin order for the user to understand the context and relationship betweenthe live video images presented in the video presentation tiles.

In a similar manner, when recorded video data is presented in a videopresentation tile of the GUI at the remote device, the recorded videodata is identified by a date and time range that represents the videodata segment selected to be streamed and presented at the videopresentation tile. Thus, while in an embodiment of the presentation ofthe recorded video data, an indication of a buffering or delay may notbe included, the similar context is maintained with respect to therecorded video data as the actual time at which the recorded video datawas acquired is presented in the video presentation tile.

In a still further embodiment as described in further detail herein, therecorded video data may be presented in a video presentation tile alongwith a navigation bar. An embodiment of the navigation bar may include avariety of options of navigation within the presentation of the recordedvideo data. Non-limiting embodiments of the functions and featuresavailable through the navigation bar may include “jump forward” and“jump backwards” options. In an exemplary embodiment, the “jump forward”feature extends the duration of the selected recorded video for playbackin the video presentation tile by extending an end time of the selectedrecorded video data segment by a set amount. In merely exemplaryembodiments this set amount may be 5 minutes, 10 minutes, or 15 minutes.Similarly, the “jump backwards” feature may extend the duration of theselected recorded video data segment presented at the video presentationtile by moving the start time of the selected recorded video datasegment earlier by a set amount. In one embodiment, in addition toextending the duration of the selected recorded video data for playback,the “jump backward” feature also restarts the streaming of the recordedvideo data at the new start time.

In still further embodiments as will be described in further detailherein, for cameras for which both live and recorded video data areavailable, a toggle switch may be presented in the video presentationtile such that a user can switch between the live streaming videoacquired by the camera and recorded video data from that same camera. Inan exemplary embodiment, the toggle switch may he presented in anavigation bar which is selectively active within the video presentationtile.

FIG. 4 is a flow chart that depicts an exemplary embodiment of a method400 of mobile video management, particularly management of thepresentation of streaming video data in the GUI presented at the remotedevice as described above with respect to FIGS. 1-3. At 402 a graphicaluser interface for streaming video is initialized. Exemplary embodimentsof such a graphical user interface will be described in further detailherein with respect to the exemplary screen shots of such a graphicaluser interface presented in FIGS. 5-9.

At 404 a selection of live video data is received exemplarily byreceiving a user input associated with a selection of a camera from alist or menu of cameras with available live video data. The screen shotof FIG. 5 exemplarily depicts an embodiment of a list of cameras, aswill be described in further detail herein. Next, at 406, a selection ofa video presentation tile is received. In an exemplary embodiment, theselection may be a user input associated with a particular videopresentation tile, such as a tap gesture received by a touch-sensitivedisplay within one of the video presentation tiles. In a still furtherembodiment, the selections of 404 and 406 may exemplarily be a drag anddrop input from the list of available cameras to one of the videoplayback tiles. At 408 live video is streamed in the selected videopresentation tile.

At 410 a selection of recorded video data is received. Such a selectionof recorded video data may be a user input associated with anidentification of a camera from which recorded video data has beenacquired. At 412 a selection of a date and time of the recorded videodata for presentation is received. Such a selection of a date and/ortime may be received by a series of user inputs, exemplarily as promptedby in the exemplary screen shot of a GUI depicted in FIG. 6. After theselection of the date and time of the selected recorded video data isreceived at 412, then a selection of the video presentation tile whichto present the recorded video data is received at 414. The recordedvideo data is then streamed for presentation in the selected videopresentation tile at 416.

In embodiments, once video data, either live or recorded is beingpresented in one or more video presentation tiles, various user inputsor actions can be taken to manipulate or modify the presentation of thevideo data in the graphical user interface.

At 418 a user input is received in a video presentation tile that ispresenting streaming video data. In a non-limiting embodiment, the userinput may be a single finger single tap gesture received with a touchsensitive graphical display of the remote device. At 420 the receiveduser input brings up a navigation bar within the video presentationtile. A merely exemplary embodiment of a navigation bar is depicted inthe exemplary screen shot found in FIG. 8 and the navigation bar mayinclude a slide bar for a user to navigate within a selection ofrecorded video data, or to toggle between recorded video and live videodata, if available. In still further embodiments, as described above, a“jump backward” feature or a “jump forward” feature may be available tomodify the duration of a selected recorded video data for presentation.

At 422 a navigation input is received in the navigation bar. Thepresentation of the streaming video in the video presentation tile ismodified according to the received navigation input, exemplarily tochange the time of the video data, or to increase the duration of thereceived video data. At 424, the GUI may operate to remove or hide thenavigation bar if the navigation bar “times out” without receiving auser input. Such a “time out” may occur if exemplarily 10 or 15 secondselapses without a user input in the navigation bar.

At 426 a user input may be received in a video presentation tile that iscurrently presenting a stream of video data, which may be live videodata or may be recorded video data. In a non-limiting embodiment, theuser input may be a single finger double tap gesture received by a touchsensitive graphical display of the remote device. Upon receiving thisinput, at 428, the streaming video data is expanded to the full extentof the video presentation tile. Thus, by a single user input, the usercan expand the streaming video data to fill the extent of the videopresentation tile for expanded viewing of the streaming video data. Inan exemplary embodiment, a user may be able to define a setting or makea predetermined selection between multiple expansion techniques. In afirst expansion technique, the streaming video data is stretched in thevertical and horizontal dimension to the full area of the videopresentation tile. In an alternative embodiment, which may be referredto as a “keep ratio” setting, the aspect ratio of the streaming videodata is maintained and presentation of the video data is expanded to thelargest size that maintains the streaming video aspect ratio with thevideo presentation tile. In such an embodiment, a portion of the videopresentation tile may not be used if the aspect ratio of the streamingvideo data does not match the aspect ratio of the video presentationtile. In a still further embodiment of an exemplary “keep ratio”setting, the aspect ratio may be maintained but the streaming video datais expanded such that the entire area of the video presentation tile isused for video presentation, although a portion of the streaming videodata may be cropped in either the horizontal or the vertical dimension.Upon receiving a second user input, exemplarily a single finger doubletap user input, in the video presentation tile at 430, the streamingvideo data is returned to a normal playback at 432.

In a still further embodiment, a user m out may be received in a videopresentation tile at 434. Exemplarily, this user input may be a doublefingered double tap gesture received by a touch sensitive graphicaldisplay of the remote device. Upon the receiving such a user input inthe video presentation tile, the GUI expands the streaming video datafrom the video presentation tile to a full screen presentation of thestreaming video data within the full screen of the GUI at 436. In anexemplary embodiment, similar expansion settings as described above withrespect to 428 may similarly apply to the expansion to the full screenof the GUI at 436. The presentation of the expanded streaming video datamay continue until at 438 another user input is received in the GUI,exemplarily another double fingered double tap gesture at which point at440 the streaming video data is returned to a normal presentation in theoriginal video presentation tile.

As stated above, FIGS. 5-9 present exemplary embodiments of screen shotsof a graphical use interface in accordance with embodiments of thesystems, methods, and software as disclosed herein. FIG. 5 depicts ascreen shot 500 of an exemplary embodiment of a list or menu ofavailable cameras. In an embodiment, the list of cameras may list thecameras on a location by location basis, or may present all availablecameras or cameras that are available within a particular network. In anexemplary embodiment, the camera list 502 includes a camera name 504, apreview view of the video data acquired at that camera 506 and anaccessories or options toggle 508 which is described in further detailherein. In an exemplary embodiment, if a particular camera is offline orunavailable, then an indication may be presented in the preview box 506to show that there is currently no live video data available. In a stillfurther embodiment, a search box 510 is presented m order for the userto quickly filter or search through camera names.

In a merely exemplary embodiment, the camera list 502 horizontallyslides into the graphical user interface in a manner that horizontallydisplaces video presentation tiles 512 off of the screen as viewed inthe GUI. In an exemplary embodiment, by toggling the “camera” button 514the camera list is introduced or hidden from the GUI and exemplarily, afull view of the video presentation tiles may be returned when thecamera list 502 is hidden.

As reference above, FIG. 6 presents an exemplary embodiment of a screenshot 600 that exemplarily depicts a graphical user interface for theselection of a date and/or time duration of recorded video data forstreaming presentation in a video presentation tile. The selected videodata may be defined by a combination of a date and a start time and anend time. In the exemplary embodiment, the selected video data wouldhave a duration of 5 minutes, from 2:54 p.m. to 2:59 p.m. on June 20.

FIG. 7 depicts an exemplary embodiment of a screen shot 700 of agraphical user interface 702 which may exemplarily be presented on atablet style mobile device and exemplarily in a horizontal or landscapeorientation. The GUI 702 includes a camera list 704 as described abovewith respect to FIG. 5, and a recorded video selection 706, as describedabove with respect to FIG. 6. In the GUI 702 of the screen shot 700, aplurality of video presentation tiles 708 are arranged within the GUI702. In a non-limiting embodiment, the user can select and position thevideo data from a camera by dragging and dropping the selected camerafrom the cameras list 704 to one of the video presentation tiles 708. Inan exemplary embodiment, the user may drag and drop a selected camerafrom the camera list 704 into one of the video presentation tiles 708 inorder to initiate streaming of a live video stream from that camera,while the user may drag and drop the recorded video data selection box706 into a video presentation tile 708 in order to initiate streamingvideo presentation of the selected recorded video data.

In an exemplary embodiment, a default mode may maintain the work spacewith the video presentation tile 708 always partially visible on a righthand side of the GUI 702. In a non-limiting embodiment, the user mayswitch between a view of solely the work space comprising the videopresentation tile 708 or a combined presentation that includes thecamera list 704 by a user input, exemplarily a left or right horizontalsliding gesture. In a still further embodiment, the GUI 702 may beoperated in a “pinned” mode. In a “pinned'” mode the left hand view thatincludes the camera list 704 is maintained and the work space thatcomprises the video presentation tile 708 is scaled to remain fullyvisible.

FIG. 8 depicts an exemplary embodiment of a screen shot 800 of agraphical user interface 802 that presents a plurality of videopresentation tile 804 that each present streaming video data. Asdescribed above, the presentation of the streaming video data in a videopresentation tile 804 may further include an identification of thecamera 806 from which the data was acquired and an indication of anybuffer, lag, or delay between streaming live video data and when thelive video data was acquired. This may also include an indication of theactual time at which the streaming video was acquired.

As exemplarily depicted with camera 3, indicated by numeral 801, thepresentation of recorded video data may include an identification of astart time 812 of the selected video data and an end time 814 of theselected video data, and a current time of the streaming video data. Anavigation bar 818 may present this information and may also provide anavigation slider 820 that facilitates a user input to navigate withinthe duration of the selected recorded video data for streaming playback.

The navigation bar 818 may further include a “jump backward”' button 822and a “jump forward” button 824 that may facilitate a user input toquickly change the recorded video duration by extending the start timeearlier by a set amount or extending the end time later by a set amount.As previously noted, in an exemplary embodiment, if the “jump backward”button 822 is selected, the streaming video may restart videopresentation at the new modified start time.

As a still further exemplary embodiment, the navigation bar 818 mayfurther include a live/recorded toggle 826 wherein if the videopresentation tile is currently presenting a stream of recorded videodata, activation of the toggle 826 will present live video from the samecamera, if available. Similarly, if live video data from a camera isbeing streamed to the video presentation tile and the toggle 826 isactivated then the user may he prompted to select a time and date todefine a duration of recorded video data from that camera to present inthe video presentation tile.

FIG. 9 depicts a still further exemplary embodiment of a screen shot 900that depicts an exemplary embodiment of a GUI 902 which includes fourvideo presentation tiles, exemplary 904, 906, 908, and 910. In theexemplary embodiment depicted in FIG. 9, the GUI 902 further includes alayout bar 912 that presents a variety of video presentation tilelayouts from which a user may select for the layout of the videopresentation tiles in the GUI 902. In an exemplary embodiment, the GUI902 includes four video presentation tiles, however, it is to berecognized that in alternative embodiments any number of presentationtiles may be contemplated in the present disclosure.

The functional block diagrams, operational sequences, and flow diagramsprovided in the Figures are representative of exemplary architectures,environments, and methodologies for performing novel aspects of thedisclosure. While, for purposes of simplicity of explanation, themethodologies included herein may be in the form of a functionaldiagram, operational sequence, or flow diagram, and may be described asa series of acts, it is to be understood and appreciated that themethodologies are not limited by the order of acts, as some acts may, inaccordance therewith, occur in a different order and/or concurrentlywith other acts from that shown and described herein. For example, thoseskilled in the art will understand and appreciate that a methodology canalternatively be represented as a series of interrelated states orevents, such as in a state diagram. Moreover, not all acts illustratedin a methodology may be required for a novel implementation.

This written description uses examples to disclose the invention,including the best mode, and also to enable any person skilled in theart to make and use the invention. The patentable scope of the inventionis defined by the claims, and may include other examples that occur tothose skilled in the art. Such other examples are intended to be withinthe scope of the claims if they have structural elements that do notdiffer from the literal language of the claims, or if they includeequivalent structural elements with insubstantial differences from theliteral languages of the claims.

1. A method of mobile video display and management, the methodcomprising: acquiring a plurality of streams of live video data from aplurality of cameras; presenting, at a remote device, available streamsof live video data; receiving a selection of one or more availablestreams of live video data for presentation at the remote device; andpresenting, at the remote device, each selected stream of live videodata and a corresponding delay indication that describes how close thestream of live video data is to real-time.
 2. The method of claim 1,wherein the delay indication is a time stamp time that identifies thetime at which the steam of live video data was acquired by the camera.3. The method of claim 1, wherein the delay indication comprises a timecorresponding to the difference between real time and the current timeof the stream of live video data.
 4. The method of claim 3, wherein thedelay indication comprises an indication of the source of the delay. 5.The method of claim 4, wherein the source of the delay is buffering. 6.The method of claim 4, wherein the source of the delay is processing. 7.The method of claim 4, wherein the source of the delay is dataconnectivity.
 8. The method of claim 1, wherein the receiving aselection of one or more available streams of live video data forpresentation at the remote device comprises: presenting a list ofcameras that are (i) acquiring a streams of live video data and (ii)available, and receiving a selection front the list.
 9. The method ofclaim 1, further comprising: initiating a graphical user interface atthe remote device for video data presentation, the graphical userinterface comprising a plurality of video presentation tiles; presentingeach selected stream of live video data and its corresponding delayindication in a particular video presentation tile.
 10. The method ofclaim 9, further comprising: receiving a selection of a graphical userinterface layout; and presenting the plurality of video presentationtiles in the graphical user interface according to the selectedgraphical user interface layout.
 11. The method of claim 10, furthercomprising: rearranging the presentation of the stream of live videodata in the graphical user interface by receiving one or more dragginginputs to move the presentation of the stream of live video data and itscorresponding delay indication to another video presentation tile of theplurality of video presentation tiles.
 12. The method of claim 9,further comprising: receiving a gesture input in a video presentationtile of the graphical user interface; and opening a navigation bar inthe video presentation tile.
 13. The method of claim 9, furthercomprising: receiving a gesture input in a video presentation tile ofthe graphical user interface; and expanding the stream of live videodata presented in the video presentation tile to fill the videopresentation tile.
 14. The method of claim 9, further comprising:receiving a gesture input in a video presentation tile of the graphicaluser interface; and expanding the stream of live video data presented inthe video presentation tile to fill the graphical user interface.
 15. Asystem for mobile video display and management, the system comprising: aplurality of video cameras that each capture a stream of live videodata; and a mobile device communicatively coupled to the video camerasvia a communication network, the mobile device comprising a graphicaldisplay and a processor, wherein the processor is configured by softwareto: acquire streams of live video data from the plurality of videocameras, wherein each stream of live video data includes a time stamp,compute, using the time stamp, a delay for each stream of live videodata, and present each of the streams of live video data and a delayindication in a graphical user interface presented on the graphicaldisplay, wherein the delay indication presented with a steam of livevideo data describes how close the stream of live video data is toreal-time.
 16. The system of claim 15, wherein the graphical userinterface comprises a plurality of video presentation tiles, whereineach video presentation tile displays one of the streams of live videodata and the delay indication corresponding to the stream of live videodata.
 17. The system of claim 16, wherein the graphical user interfacecomprises a menu of video cameras that are available for streaming livevideo data, and a user selection from the menu causes the graphical userinterface to present the selected stream of live video data in one ofthe video presentation tiles.
 18. The system of claim 15, wherein acamera indication is presented with each stream of live video data in apresentation tile, the camera indication specifying the camera thatcaptured the stream of live video data.
 19. The system of claim 15,wherein the delay indication and camera indication are overlaid on thestream of live video data in the video presentation tile.
 20. Anon-transient computer readable medium programmed with computer readablecode that upon execution by a computer processor causes the processorto: acquire streams of live video data from a plurality of videocameras, wherein each stream of live video data includes a time stamp,compute, using the time stamp, a delay for each stream of live videodata, and present each of the streams of live video data and a delayindication in a graphical user interface, wherein the delay indicationpresented with a steam of live video data describes how close the streamof live video data is to real-time.